Skip to main content

This is a new service – your feedback will help us to improve it.

Newcastle-under-Lyme Borough Council

Tree preservation zone

There is a problem

  • tree-preservation-order column must match the reference field in the tree preservation order dataset

entity: 19206478

reference
T7-1\TPO0001_W1
name
tree-preservation-order

undefined

T7-1\TPO0001
tree-preservation-zone-type
woodland
geometry
MULTIPOLYGON (((-2.303684 53.019155,-2.304026 53.019212,-2.304154 53.019250,-2.304219 53.019320,-2.304315 53.019352,-2.304508 53.019384,-2.304603 53.019390,-2.304770 53.019346,-2.304660 53.019263,-2.304609 53.019237,-2.304281 53.019101,-2.304149 53.019018,-2.304061 53.018957,-2.304003 53.018874,-2.303987 53.018782,-2.304008 53.018641,-2.304051 53.018527,-2.304087 53.018474,-2.304130 53.018400,-2.304202 53.018224,-2.304245 53.018105,-2.304273 53.017978,-2.304273 53.017908,-2.304187 53.017818,-2.304143 53.017702,-2.303799 53.017333,-2.303735 53.017256,-2.303542 53.017237,-2.303326 53.017185,-2.303200 53.017081,-2.302964 53.016878,-2.302621 53.016705,-2.302525 53.016751,-2.302440 53.016854,-2.302473 53.016912,-2.302500 53.016964,-2.302736 53.017129,-2.302977 53.017290,-2.303009 53.017322,-2.303673 53.017636,-2.303803 53.017906,-2.303825 53.017970,-2.303804 53.018041,-2.303741 53.018131,-2.303720 53.018266,-2.303721 53.018369,-2.303679 53.018421,-2.303562 53.018492,-2.303531 53.018582,-2.303520 53.018627,-2.303564 53.018737,-2.303650 53.018826,-2.303671 53.018859,-2.303629 53.018949,-2.303565 53.018988,-2.303406 53.019046,-2.303459 53.019072,-2.303531 53.019069,-2.303630 53.019043,-2.303684 53.019155)))
point
POINT (-2.303684 53.018043)
notes
entry-date
2026-07-28
start-date
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The Tree preservation zone guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that covers this zone.

How to improve Newcastle-under-Lyme Borough Council’s data

  1. Fix the errors indicated
  2. Use the check service to make sure the data meets the standard
  3. Publish the updated data on the endpoint URL